Wearable device multi-mode system

ABSTRACT

Systems and techniques are disclosed for detecting whether a wearable computing device is worn by a user or not. The detection can be made based on whether the device is secured to a user or based on a sensor. A device worn by a user may be operated in a private mode such that the user wearing the device is provided information that is useful while wearing the device. For example, the user may receive message notifications, news updates, telephone call information, or the like. A wearable computing device maybe operated in a public mode while not being worn by a user. While in the public mode, the device may provide non user specific information such as a current time, media items, or the like.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/420,931, filed on Jan. 31, 2017, which is a continuation of U.S.application Ser. No. 13/914,875, filed on Jun. 11, 2013, and issued asU.S. Pat. No. 9,569,625 on Feb. 14, 2017, the disclosure of which areincorporated herein by reference.

BACKGROUND

Traditional wearable devices, such as wrist watches, eyewear, and thelike, are limited in space and size, resulting in a low number ofbuttons and/or a restricted surface area that a user can interact with.The limited space and size may restrict the capability of a wearabledevice and/or require a user to shift through multiple menus toaccomplish a task, such as to modify a device state. Accordingly, a usermay be less motivated to use a wearable device as use of the devicewould require the user to maneuver through an unacceptable number ofmenus or to operate a device that is cumbersome difficult to use.Additionally, a wearable device may operate via battery power and maygenerally operate in a single state. Based on operating in the singlestate, the device may lose battery power at the same rate whether or notthe device is worn by a user, effectively wasting the lost batterypower.

BRIEF SUMMARY

According to implementations of the disclosed subject matter, a wearablecomputing device may be detected as worn by a user and, based on thedetection, the wearable computing device may operate in a private modein which one or more private data elements are provided to the user,which are not available when the device is not in the private mode. Thewearable computing device may be detected as not worn by a user and,based on the detection, the wearable computing device may operate in apublic mode in which the device provides one or more data elements thatare not secure, and in which it may not provide private data elements.An electronic device such as a mobile phone, tablet, laptop computer,desktop computer, server, hard drive, or the like may provide theprivate data element to the wearable electronic device. The electronicdevice may also determine whether a data element is a private dataelement or a public data element. Alternatively, the wearable computingdevice may determine whether a data element is a private data element ora public data element. Whether a wearable computing device is worn by auser or not may be determined by detecting whether a securable portionof the wearable computing device, such as a clasp, buckle, or fasteneris secured. Alternatively, a capacitance, conductance, galvanic skinresponse, accelerometer, heartbeat monitor, or a device with amicroprocessor may be used to make the determination.

Systems and techniques according to the present disclosure allow thearrangement to determine whether to operate a wearable device in aprivate or public mode based on whether it is determined that the deviceis being worn by a user, or likely to be worn by a user. Additionalfeatures, advantages, and implementations of the disclosed subjectmatter may be set forth or apparent from consideration of the followingdetailed description, drawings, and claims. Moreover, it is to beunderstood that both the foregoing summary and the following detaileddescription include examples and are intended to provide furtherexplanation without limiting the scope of the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the disclosed subject matter, are incorporated in andconstitute a part of this specification. The drawings also illustrateimplementations of the disclosed subject matter and together with thedetailed description serve to explain the principles of implementationsof the disclosed subject matter. No attempt is made to show structuraldetails in more detail than may be necessary for a fundamentalunderstanding of the disclosed subject matter and various ways in whichit may be practiced.

FIG. 1 shows a computer according to an implementation of the disclosedsubject matter.

FIG. 2 shows a network configuration according to an implementation ofthe disclosed subject matter.

FIG. 3 shows an example process for determining an operation mode,according to an implementation of the disclosed subject matter.

FIG. 4a shows an example illustration of a wearable unclasped watch,according to an implementation of the disclosed subject matter.

FIG. 4b shows an example illustration of a wearable clasped watch,according to an implementation of the disclosed subject matter.

FIG. 5 shows an example illustration of the reverse side of a watch,according to an implementation of the disclosed subject matter.

FIG. 6a shows an example illustration of a mobile phone transmitting toa clasped watch, according an implementation of the disclosed subjectmatter.

FIG. 6b shows an example illustration of a mobile phone transmitting toan un-clasped, according an implementation of the disclosed subjectmatter.

FIG. 7 shows an example illustration of computing eyewear, according toan implementation of the disclosed subject matter.

DETAILED DESCRIPTION

Enabling a wearable computing device to automatically modify a use modecan improve device battery life, allow secured data distribution, allowpersonalized data distribution, and have additional benefits asdisclosed herein. According to implementations disclosed herein, whetherthe device is being worn by a user, or likely to be worn by a user maybe based on a secured clasp, buckle, fastener or based on measuring acapacitance, capacitance, galvanic skin response, or any otherapplicable technique. The arrangement may operate the wearable computingdevice in a private mode if the device is determined to likely be wornby a user. As disclosed herein, the private mode operation may includeconfigurations and specific data disclosure such as providing a userwith email messages that are associated with a user email account. Itmay be beneficial to operate a wearable computing device in a differentmode while the device is worn (i.e. private mode) than while the deviceis not worn (i.e., public mode). Using different modes when appropriatemay enable efficient battery consumption. For example, more data may bereceived and/or transmitted by the wearable computing device while it isin a private mode as a user may benefit from the data transfer. Asanother example, more information may be displayed on the wearablecomputing device display when in a private mode, because it is morelikely that a user wearing the device will receive the information. Asanother example, the wearable computing device display may be brighterwhen the device is in a private mode as a user is more likely to viewthe display, and save battery power by operating at a differentbrightness when in the public mode. Using different modes also maysecure private data, for example by only displaying private data whilein a private mode. As another example, communication with anotherelectronic device may vary based on private and public modes. The use ofmultiple modes as disclosed herein also may provide personal data. Forexample, user specific data may be received and provided to a user inthe private mode, the wearable computing device may communicate with aspecific user electronic device based on the operating in a private modeand the user wearing the device, etc.

A user may be authenticated prior to operating the wearable computingdevice in a private mode by using techniques disclosed herein such asinputting a pin-code, providing biometric data, and the like. Thearrangement may operate the wearable computing device in a public modeif the device is determined to not be worn by a user or not likely to beworn by a user. As disclosed herein, the public mode operation mayinclude configurations and general data disclosure such as allowingmedia playback from the wearable computing device or displaying acurrent time on the device display. As a specific example, a wrist watchwith a display screen may operate in a public mode while unclasped andplaced inside a cupboard. While in the public mode, the watch mayoperate at 10% brightness and display a current time. Subsequently, thewatch may be extracted from the cupboard and secured on a user's wristby placing the watch around the user's wrist and securing it by claspingthe watch band. The arrangement may determine that the user is wearingthe wrist watch and require the user to input a pin-code in order tooperate the wrist watch in a private mode. Receiving an incorrectpin-code may result in continued operation of the wrist watch in thepublic mode. Receiving a correct pin-code may result in operating thewrist watch in a private mode such that the user is able to receivepersonalized information such as emails and/or interact with the wristwatch in a manner that is distinct from interaction with the wrist watchwhile it operates in the public mode.

Implementations of the presently disclosed subject matter may beimplemented in and used with a variety of component and networkarchitectures. FIG. 1 is an example computer 20 suitable forimplementing implementations of the presently disclosed subject matter.The computer 20 may correspond to a wearable computing device or may bea part of the wearable computing device. The computer 20 includes a bus21 which interconnects major components of the computer 20, such as acentral processor 24, a memory 27 (typically RAM, but which may alsoinclude ROM, flash RAM, or the like), an input/output controller 28, auser display 22, such as a display or touch screen via a displayadapter, a user input interface 26, which may include one or morecontrollers and associated user input or devices such as a keyboard,mouse, WiFi/cellular radios, touchscreen, microphone/speakers and thelike, and may be closely coupled to the I/O controller 28, fixed storage23, such as a hard drive, flash storage, Fibre Channel network, SANdevice, SCSI device, and the like, and a removable media component 25operative to control and receive an optical disk, flash drive, and thelike.

The bus 21 allows data communication between the central processor 24and the memory 27, which may include read-only memory (ROM) or flashmemory (neither shown), and random access memory (RAM) (not shown), aspreviously noted. The RAM can include the main memory into which theoperating system and application programs are loaded. The ROM or flashmemory can contain, among other code, the Basic Input-Output system(BIOS) which controls basic hardware operation such as the interactionwith peripheral components. Applications resident with the computer 20can be stored on and accessed via a computer readable medium, such as ahard disk drive (e.g., fixed storage 23), an optical drive, floppy disk,or other storage medium 25.

The fixed storage 23 may be integral with the computer 20 or may beseparate and accessed through other interfaces, such as an electronicdevice, as disclosed herein. A network interface 29 may provide a directconnection to a remote server via a telephone link, to the Internet viaan internet service provider (ISP), or a direct connection to a remoteserver via a direct network link to the Internet via a POP (point ofpresence) or other technique. The network interface 29 may provide suchconnection using wireless techniques, including digital cellulartelephone connection, Cellular Digital Packet Data (CDPD) connection,digital satellite data connection or the like. For example, the networkinterface 29 may allow the computer to communicate with other computersvia one or more local, wide-area, or other networks, as shown in FIG. 2.

Many other devices or components (not shown) may be connected in asimilar manner (e.g., document scanners, digital cameras and so on).Conversely, all of the components shown in FIG. 1 need not be present topractice the present disclosure. The components can be interconnected indifferent ways from that shown. The operation of a computer such as thatshown in FIG. 1 is readily known in the art and is not discussed indetail in this application. Code to implement the present disclosure canbe stored in computer-readable storage media such as one or more of thememory 27, fixed storage 23, removable media 25, or on a remote storagelocation.

FIG. 2 shows an example network arrangement according to animplementation of the disclosed subject matter. One or more clients 10,11, such as wearable computing devices, local computers, smart phones,tablet computing devices, and the like may connect to other devices viaone or more networks 7. The network may be a local network, wide-areanetwork, the Internet, or any other suitable communication network ornetworks, and may be implemented on any suitable platform includingwired and/or wireless networks. The clients may communicate with one ormore servers 13 and/or databases 15. The devices may be directlyaccessible by the clients 10, 11, or one or more other devices mayprovide intermediary access such as where a server 13 provides access toresources stored in a database 15. The clients 10, 11 also may accessremote platforms 17 or services provided by remote platforms 17 such ascloud computing arrangements and services. The remote platform 17 mayinclude one or more servers 13 and/or databases 15.

More generally, various implementations of the presently disclosedsubject matter may include or be implemented in the form ofcomputer-implemented processes and apparatuses for practicing thoseprocesses. Implementations also may be implemented in the form of acomputer program product having computer program code containinginstructions implemented in non-transitory and/or tangible media, suchas floppy diskettes, CD-ROMs, hard drives, USB (universal serial bus)drives, or any other machine readable storage medium, wherein, when thecomputer program code is loaded into and executed by a computer, thecomputer becomes an apparatus for practicing implementations of thedisclosed subject matter. Implementations also may be implemented in theform of computer program code, for example, whether stored in a storagemedium, loaded into and/or executed by a computer, or transmitted oversome transmission medium, such as over electrical wiring or cabling,through fiber optics, or via electromagnetic radiation, wherein when thecomputer program code is loaded into and executed by a computer, thecomputer becomes an apparatus for practicing implementations of thedisclosed subject matter. When implemented on a general-purposemicroprocessor, the computer program code segments configure themicroprocessor to create specific logic circuits. In someconfigurations, a set of computer-readable instructions stored on acomputer-readable storage medium may be implemented by a general-purposeprocessor, which may transform the general-purpose processor or a devicecontaining the general-purpose processor into a special-purpose deviceconfigured to implement or carry out the instructions. Implementationsmay be implemented using hardware that may include a processor, such asa general purpose microprocessor and/or an Application SpecificIntegrated Circuit (ASIC) that implements all or part of the techniquesaccording to implementations of the disclosed subject matter in hardwareand/or firmware. The processor may be coupled to memory, such as RAM,ROM, flash memory, a hard disk or any other device capable of storingelectronic information. The memory may store instructions adapted to beexecuted by the processor to perform the techniques according toimplementations of the disclosed subject matter.

According to an implementation of the disclosed subject matter, as shownat step 300 in FIG. 3, the arrangement may determine whether a wearablecomputing device is worn by a user or likely worn by a user. Determiningwhether a wearable computing device is worn or likely worn by a user mayenable the arrangement to operate the device in a respective mode. Forexample, a private mode configured to drive a display on the wearablecomputing device at 100% brightness may be suitable while the device isworn and, accordingly, determining that the device is worn may result inoperating the device in the private mode.

A wearable computing device may be designated as worn or likely worn bya user based on whether a securable component of the device is secured.The securable component may be any applicable component such as a clasp,a buckle, a fastener, or the like. For example, as shown in FIG. 4a , awrist watch 400 may contain two fastening components, a first claspcomponent 410 and a second clasp component 420. The arrangement maydetermine that the wrist watch is not worn or not likely worn by a userwhile the first clasp component 410 and the second clasp component 420are not connected. A connection may be determined based on an electronicsignal that propagates through at least a portion of the wearablecomputing device. Continuing the previous example, an electronic signalmay be propagated towards one end of the wrist watch such that a circuitis not complete unless the first clasp component 410 and second claspcomponent 420 are connected. Accordingly, the arrangement may determinethat the wrist watch is not worn or not likely not worn by a user if itdetects that the circuit is not completed. Alternatively, as shown inFIG. 4b , the wrist watch 400 may be worn by a user and secured byconnecting the first clasp component 410 and second clasp component 420.An electric circuit may be completed when the clasps are connected and,accordingly, the arrangement may determine that the wrist watch is wornby a user. It will be understood that although a completed circuit isspecifically disclosed as an example, any applicable signal detectionmay be utilized to establish the state of a wearable computing device.

The arrangement may determine whether a wearable computing device isworn or likely worn by a user by using any applicable sensor such as acapacitance sensor, a skin conductance sensor, an accelerometer, amicroprocessor device, a biometric sensor (e.g., a heartbeat monitor), alight sensor, motion sensor, or the like. A capacitance sensor may beused to detect an electrical capacitance and may be located on thewearable computing device such that it is able to detect capacitance ona human body when the device is worn. As an example, as shown in FIG. 5,a wrist watch 500 may contain a capacitance sensor on the back side 510such that when a user wears the wrist watch, the capacitance sensor isable to detect a capacitance from the user's body. The arrangement maydetermine that a user is wearing or likely wearing a wearable computingdevice when the capacitance sensor registers a threshold capacitancevalue and that a user is not wearing or not likely wearing the deviceabsent a registered threshold capacitance value. As another example, asshown in FIG. 7, the arrangement may determine that a user 710 iswearing or likely wearing eyewear 720 based on a capacitance readingobtained by either eyewear component 724 or 726.

Similarly, a skin conductance (e.g., a galvanic skin response,electrodermal response, psychogalvanic reflex, skin conductanceresponse, skin conductance level, etc.) may be measured using anyapplicable component. The arrangement may determine whether a user iswearing or likely wearing a wearable computing device based on athreshold conductance value. Similarly, a biometric sensor may gatherany applicable biometric data such as a heartbeat, physical pattern(e.g., iris pattern, retina patter, facial pattern, etc.) electricfield, magnetic field, odor, sound, or the like. As an example, awearable computing device may contain a sensor that can detect anelectric field generally generated by humans and may be configured todetect an electric filed passing through at least a portion of thedevice. The arrangement may determine whether a user is wearing orlikely wearing a wearable computing device based on detecting theelectrical field. A light sensor may detect any applicable light basedattribute such as brightness, intensity, luminance, color, or the like.

According to an implementation, the arrangement may determine whether awearable computing device is worn by a user based on a single sensorand/or attribute or based on a combination of sensors and/or attributes.A combination of sensors and/or attributes may provide a more robustresult as they may enable the arrangement to apply multiple data valuesto determine whether a user is wearing or likely wearing wearablecomputing device. As an example, the arrangement may determine that awearable computing device is not worn by a user if a motion sensorlocated within the device has not reported a threshold amount ofmovement within 15 minutes and if the light sensor detects a luminancevalue of below 3 cd/m². As another example, the arrangement maydetermine that a wearable computing device is worn by a user if athreshold skin conductance amount is detected by a sensor as well as ifa motion sensor has detected movement within the past 20 minutes.

According to an implementation of the disclosed subject matter, at step310 in FIG. 3, the arrangement may determine that a wearable computingdevice is worn or likely worn by a user. Based on the determination, asshown at step 320, the wearable computing device may be operated in aprivate mode. The private mode may be associated with elements such asdata, data types, configurations, and the like. At step 330, thewearable computing device may receive, transmit and/or provide data to auser that the device in another mode (e.g., public mode) does not. Thedata may be identified as private data by the wearable computing deviceor by another electronic device, as disclosed herein. The data may beprivate such that a user may not intend to distribute the type of datapublically or allow another user to view the data. As an example, thewearable computing device may receive a user setting and, based on theuser setting, may display the user's work related calendar events onlywhen the device is in a private mode. The user setting may be input viathe wearable computing device or an external device, as disclosedherein. The arrangement may be configured such that a data type is onlyreceived, transmitted and/or provided by the wearable computing devicewhile the device is in a private mode. The data type may be one suchthat a user may not intend to distribute the type of data publically orallow another user to view the type of data. As an example, a watchoperating in a private mode may receive banking alerts from a user'sbanking service and provide the banking alerts to a user via a displayon the watch only when the watch is operating in a private mode.Alternatively or in addition, the data type may be one such thatreceiving, transmitting, and or providing the data type by the wearablecomputing device would be inefficient unless the device is operating ina private mode. A data type may be inefficient for any applicable reasonsuch as for battery consumption, for providing non-applicableinformation, or the like. As an example, a wearable computing device maydisplay email alerts via a display screen only while the device is in aprivate operating mode as if the device is in a public mode, it islikely that the device is not worn by a user and, thus, the alerts willnot be useful to a user. Further, providing the alerts may consumeadditional battery power in comparison to not providing the alerts and,thus, the alerts may only be provided to the user while the device is ina private mode (e.g., while it is worn or likely worn by a user) and notwhile it is in a public mode, to reduce battery consumption. Either thewearable computing device or an electronic device may determine whethera data, data type, or configuration is private (e.g., secure, personal,inefficient, etc.), as disclosed herein.

A wearable computing device operating in a private mode may beconfigured differently than the device operating in another mode (e.g.,a public mode). The configuration may apply any applicable property suchas a brightness (e.g., the display may operate at a higher brightness),frequency of an event (e.g., more frequent message alerts, more frequentreminders, more frequent notifications, etc.), providing data for a typeof event (e.g., private messages, private data, data useful while adevice is worn by a user, etc.), communicating with an electronic device(e.g., communicating with a mobile phone, tablet, computer, server,etc.), or the like. A wearable computing device may have access to auser account, such as an email account, banking account, social mediaaccount, purchasing account, media account, or the like, and mayreceive, transmit, and/or provide data to a user based on the useraccount while in a private mode. As an example, a first user's watch mayoperate in a private mode and the first user may receive an alert that asecond user has requested the first user to join the second user'ssocial network. The first user may be able to accept, reject, or ignorethe request by interacting with a touchscreen display on the watch, orby using a voice command or gesture to provide an instruction to thewatch. As another example, as shown in FIG. 7, eyewear 720 may haveaccess to a user's contact list and, when in a private mode, may enablea user to communicate with a contact by accessing the user's contactlist. According to an implementation of the disclosed subject matter, awearable computing device may be configured to be tailored to a specificuser. For example, a wearable computing device may be configured to betailored to both a brother and a sister, based on who is using thedevice. The device may determine which user to tailor the watch to at aspecific instance based on an authentication request, as disclosedherein. Accordingly, a wearable computing device operating in a privatemode may provide user specific data to a specific user based ondetermining that the specific user is wearing the device. As an example,a watch may request a user to input a pin-code prior to operating in aprivate mode. Based on the received pin-code, the watch may determinethat user two of three potential users is wearing or likely wearing thewatch and, accordingly, may provide information (e.g., email updates)that correspond to user two of three.

According to an implementation of the disclosed subject matter, at step340 in FIG. 3, the arrangement may determine that a wearable computingdevice is not worn or likely not worn by a user. Based on thedetermination, as shown at step 350, the wearable computing device maybe operated in a public mode. The public mode may be associated withelements such as data, data types, configurations, and the like. At step360, while operating in the public mode, the wearable computing devicemay receive, transmit and/or provide data to a user that is notconsidered private, secure, or inefficient (e.g., data that is unlikelyto be viewed by user, data that requires more battery to be used thanwould be efficient for an unworn device, etc.). The data may beidentified as public data by the wearable computing device or by anelectronic device, as disclosed herein. The data may be public such thata user may intend the data to be made available to anyone that isproximate to the wearable computing device. As an example, the wearablecomputing device may display a current time, date, or weather whileoperating in a public mode as the time, date or weather may beapplicable to anyone that is proximate to the device. The arrangementmay be configured such that a data type is excluded from being received,transmitted and/or provided by the wearable computing device while thedevice is in a private mode. The data type may be one such that a usermay not intend to distribute the type of data publically or allowanother user to view the type of data. As an example, a watch operatingin a public mode may not receive any banking or personal email alertsthat the device may receive while in another mode (e.g., a privatemode). Alternatively or in addition, the data type may be one such thatreceiving, transmitting, and or providing the data type by the wearablecomputing device would be inefficient while operating in a public modeas it is likely that a user is not wearing the device. A data type maybe inefficient for any applicable reason such as for batteryconsumption, for providing non-applicable information, or the like. Asan example, displaying email alerts via a display screen while a deviceis not worn by a user may compromise the user's privacy as well asconsume unnecessary battery power. Thus, email alerts may not bedisplayed while a wearable device is operating in a public mode. Eitherthe wearable computing device or an electronic device may determinewhether a data, data type, or configuration is public (e.g., generic,impersonal, efficient, etc.), as disclosed herein.

A wearable computing device operating in a public mode may be configureddifferently than the device operating in another mode (e.g., a privatemode). The public mode configuration may apply any applicable propertysuch as a brightness (e.g., the display may operate at a lowerbrightness), frequency of an event (e.g., less frequent or no messagealerts, less frequent or no reminders, less frequent or nonotifications, etc.), withholding displaying/providing data for a typeof event (e.g., private messages, private data, data useful while adevice is worn by a user, etc.), not communicating or minimallycommunicating with an electronic device (e.g., communicating with amobile phone, tablet, computer, server, etc.), displaying only aspecific type of data (e.g., time data), or the like. A wearablecomputing device with access to a user account, as disclosed herein, maynot receive, transmit, and/or provide data to a user based on the useraccount while in a public mode. As an example, a first user's watch mayoperate in a public mode and alerts and notifications that may normallybe displayed on the watch while in a private mode, may not be displayed.As another example, as shown in FIG. 7, eyewear 720 may generally haveaccess to a user's contact list while in a private mode. However, whilein a public mode, the eyewear may not have access to the contact listand, thus, may not initiate respective communication.

According to an implementation of the disclosed subject matter, awearable computing device may communicate with an electronic device. Theelectronic device may act as a hub for the wireless computing device anddata that is provided to and/or from the wireless computing device. Forexample, email data that is displayed using a wireless computing devicemay be provided by an electronic device. Additionally, an electronicdevice may be used to configure a wireless communication device. Forexample, a wrist watch may be connected to a user's mobile phone using aBluetooth connection. The user may instruct the mobile phone to providethe wireless computing device with media stored on the mobile phone.Subsequently, the user may view the media provided by the electronicdevice on a wireless computing device display screen.

An electronic device may be any applicable device configured tocommunicate with the wearable computing device such as a mobile phone, atablet, a laptop computer, a desktop computer, a server, a hard drive,or the like. The electronic device and the wearable computing device maycommunicate via any applicable connection such as a physical connection,a wired connection, a wireless connection, a Bluetooth connection, aWifi connection, a network connection, a cellular connection, or thelike. An electronic device may communicate with a wearable computingdevice and provide any applicable data such as communication alerts,communication messages, reminders, data packets, media content,documents, files, advertisements, search results, or the like. A dataelement request may be transmitted from a wearable computing device tothe electronic device or the electronic device may periodically transmitdata elements to one or more wearable computing devices. The periodictimes may be predetermined, arbitrary, or determined dynamically orbased on a rule or setting. Additionally, an electronic device maydetermine whether specific data or data type is associated with a publicor private mode. As an example, a user mobile phone may determine thatemail messages are secure data and, thus, only provide them to awearable computing device if the device is in a private mode.Alternatively, the user mobile phone may determine that email messagesare secure data and, thus, mark them as secure data such that a wearablecomputing device may determine, based on the marking, not to displaythem unless the device is in a private mode. Alternatively, as disclosedherein, the user mobile phone may provide the email messages to awearable computing device, and the device may determine that themessages are secure and, thus, only provide them to a user while in aprivate mode. Notably, an electronic device or wearable computing devicemay determine whether a data element, data type, or configuration shouldbe categorized as private or public.

According to an implementation of the disclosed subject matter, thearrangement may operate a wearable computing device in a given modebased on an electronic device. The mode may be determined based on anelectronic device configuration, location, proximity, or the like. As anexample, a user may configure an electronic device to disable a wearablecomputing device from entering a private mode. Specifically, a user mayaccess an application on the electronic device and configure the modesettings for a wearable computing device. As disclosed, theconfiguration may include a specific mode and may include time or rulebased settings. As an example, a user may configure the arrangement suchthat a wearable computing device is operated in a public mode wheneverthe user's mobile phone is in placed in a meeting mode. A wearablecomputing device mode may be modified based on the location of thewearable computing device (e.g., home, work, school, airplane, etc.)and/or on an electronic device location. As an example, the user mayconfigure the arrangement such that a wrist watch enters public modewhenever the user's electronic device is within a conference room. Awearable computing device mode may be modified based on the proximity ofan electronic device to one or more other electronic devices and/or tothe wearable computing device. As an example, the arrangement mayoperate the wearable computing device in a public mode if a specifiedelectronic device is not within a threshold proximity to the wearablecomputing device. It will be understood that a wearable computing devicemode may be determined based on a combination of factors such as, forexample, the mode may be based on whether a user is likely wearing thewearable computing device as well as on an electronic deviceconfiguration.

An electronic device may be configured to receive from or transferinformation to a wearable computing device based on whether it is likelythat a user is wearing the wearable computing device or based on themode the device is operating in. As an illustrative example, as shown inFIG. 6a , an electronic device may be provided with information thatindicates that the wrist watch 610 is worn or likely worn by a user orthat the wrist watch 610 is operating in a private mode. Accordingly,the electronic device may transfer information to the wrist watch 610.Alternatively, as shown in FIG. 6b , an electronic device may beprovided with information that indicates that the wrist watch 620 isworn or likely worn by a user or that the wrist watch 620 is operatingin a private mode. Accordingly, the electronic device may not transferinformation to the wrist watch 610.

According to an implementation of the disclosed subject matter, anauthentication element may be requested prior to operating a wearablecomputing device in a private mode. An authentication element may enablethe arrangement to verify that access to a private mode via a wearablecomputing device is only provided to an intended user. An authenticationelement may be required prior to enabling private mode access on awearable computing device. The lack of a valid authentication elementmay cause a wearable computing device to remain in a public mode. Forexample, the owner of a wrist watch may use the wrist watch to accessprivate mode data upon inputting a user specific pin code into thewearable device. The owner may allow another individual to borrow thewrist watch without providing the other individual access with the userspecific pin code and, thus, restricting the other user from beingexposed to the private mode data. The authentication element may be anyapplicable element such as a pin code (e.g., an alphanumeric code, anumeric code, a pattern code, a voice code, etc.), a biometric attribute(e.g., a heartbeat, physical pattern, iris pattern, retina patter,facial pattern, electric field, magnetic field, odor, sound, etc.), agesture (e.g., a design, a pattern, a touch gesture, a non-touchgesture, etc.), or the like. The arrangement may receive theauthentication element in any applicable manner such as via an input ona wearable computing device or electronic device (e.g., touch screeninput, hard button input, soft button input, microphone, biometricsensor input, etc.). For example, a wrist watch may enable a user toinput a pin code via a touch screen display on the face of the wristwatch. Accordingly, when a user wears the wrist watch, the wrist watchmay display a pin code input prompt and enable a user to input a pincode. Upon receiving a valid pin code, the wrist watch may enter aprivate mode or, upon receiving an invalid pin code or not receiving apin code, the wrist watch may enter or remain in a public mode.

An authentication element may be required to enter into a private modeupon detecting that a user is wearing or likely wearing a wearablecomputing device. For example, a user may wear a wrist watch and upondetecting that the user has worn the wrist watch, the user may beprompted to input an authentication element to enable the wrist watch toenter a private mode. Alternatively or in addition, an authenticationelement may be requested multiple times while a user is wearing orlikely wearing the wearable device. For example, a user may wearcomputing eyewear at the beginning of a day, and continue to wear thecomputing eyewear throughout the day. The user may be required to inputan authentication element two or more times throughout the day in orderto maintain operation of the computing eyewear. Multiple requests forauthentications may be based on predetermined criteria such as time(e.g., time intervals, times of day, etc.), location (e.g., change oflocation, presence in a specific location, etc.), or the like.Alternatively, requests for authentication may be based on the data ortype of data being accessed while in private mode. For example, a usermay input an authentication element to enable a wrist watch to operatein a private mode. Subsequently, while the wrist watch is in the privatemode, the user may request access to banking data. The arrangement mayrequire the user to provide the same authentication element or adifferent authentication element prior to providing the user access tothe banking data and/or continuing operation of the wrist watch in theprivate mode.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific implementations. However, theillustrative discussions above are not intended to be exhaustive or tolimit implementations of the disclosed subject matter to the preciseforms disclosed. Many modifications and variations are possible in viewof the above teachings. The implementations were chosen and described inorder to explain the principles of implementations of the disclosedsubject matter and their practical applications, to thereby enableothers skilled in the art to utilize those implementations as well asvarious implementations with various modifications as may be suited tothe particular use contemplated.

The invention claimed is:
 1. A method comprising: receiving, by awearable computing device from a user of the wearable computing device,user settings categorizing one or more data types of data associatedwith the user received from an electronic device as private data;determining, by the wearable computing device, whether an authenticationelement associated with the user is received; operating, by the wearablecomputing device based on the determining that the authenticationelement associated with the user is received, in a private mode;providing for display, by the wearable computing device operating in theprivate mode, data received from the electronic device categorized asprivate data based on the user settings; operating, by the wearablecomputing device based on the determining that the authenticationelement associated with the user is not received, in a public mode; andnot providing for display, by the wearable computing device operating inthe public mode, data received from the electronic device categorized asprivate data based on the user settings.
 2. The method of claim 1,wherein the authentication element associated with the user includes agesture of the user wearing the wearable computing device.
 3. The methodof claim 1, wherein the not providing for display the data received fromthe electronic device categorized as private data based on the usersettings includes blocking an alert for the data received from theelectronic device categorized as private data.
 4. The method of claim 1,wherein the providing for display the data received from the electronicdevice categorized as private data based on the user settings includesdisplaying an alert for the data received from the electronic devicecategorized as private data.
 5. The method of claim 1, wherein theoperating in the private mode further includes providing for displaycontents at a first frequency level, and the operating in the publicmode further includes providing for display contents at a secondfrequency level.
 6. The method of claim 1, wherein the operating in theprivate mode further includes providing for display contents at a firstbrightness level, and the operating in the public mode further includesproviding for display contents at a second brightness level.
 7. Themethod of claim 1, further comprising: receiving, by the wearablecomputing device operating in the private mode, data categorized asprivate data from the electronic device; not receiving, by the wearablecomputing device operating in the public mode, data categorized asprivate data from the electronic device.
 8. The method of claim 1,further comprising: receiving, by the wearable computing device from theuser of the wearable computing device, second user settings categorizingone or more data types of data associated with the user received fromthe electronic device as public data; providing for display, by thewearable computing device operating in the public mode, data receivedfrom the electronic device categorized as public data based on thesecond user settings.
 9. The method of claim 1, further comprising:determining, by the wearable computing device, that a location of thewearable computing device is a private location, wherein the operatingin the private mode is further based on the location of the wearablecomputing device being a private location.
 10. The method of claim 1,further comprising: determining, by the wearable computing device, thata location of the wearable computing device is a public location,wherein the operating in the public mode is further based on thelocation of the wearable computing device being a public location. 11.The method of claim 1, further comprising: determining, by the wearablecomputing device, that the electronic device is operating in a firstmode, wherein the operating the wearable computing device in the privatemode is further based on the electronic device operating in the firstmode.
 12. The method of claim 1, further comprising: determining, by thewearable computing device, that the electronic device is operating in asecond mode, wherein the operating the wearable computing device in thepublic mode is further based on the electronic device operating in thesecond mode.
 13. The method of claim 12, wherein the second mode is ameeting mode.
 14. The method of claim 1, further comprising: detecting,by the wearable computing device, that the electronic device is within athreshold proximity to the wearable computing device, wherein theoperating in the private mode is further based on the detecting that theelectronic device is within the threshold proximity.
 15. The method ofclaim 1, further comprising: detecting, by the wearable computingdevice, that the wearable computing device is being worn by the user,wherein the operating in the private mode is further based on thedetecting that the wearable computing device is being worn by the user.16. The method of claim 1, wherein the user settings are receivedthrough the electronic device.
 17. A wearable device, comprising: a userdisplay; and one or more processors configured to: receive, from a userof the wearable device, user settings categorizing one or more datatypes of data associated with the user received from an electronicdevice as private data; determine whether an authentication elementassociated with the user is received; operate, based on the determiningthat the authentication element associated with the user is received,the wearable device in a private mode; control, while operating thewearable device in the private mode, the user display to display datareceived from the electronic device categorized as private data based onthe user settings; operate, based on the determining that theauthentication element associated with the user is not received, thewearable device in a public mode; and control, while operating thewearable device in the public mode, the user display not to display datareceived from the electronic device categorized as private data based onthe user settings.
 18. The wearable device of claim 17, furthercomprising: one or more sensors, the one or more sensors configured todetect a gesture of the user wearing the wearable device as theauthentication element associated with the user.
 19. The wearable deviceof claim 17, wherein the one or more processors are further configuredto: control the user display to display contents at a first frequencylevel while operating the wearable device in a private mode; and controlthe user display to display contents at a second frequency level whileoperating the wearable device in a public mode.
 20. The wearable deviceof claim 17, wherein the one or more processors are further configuredto: determine that a location of the wearable device is a privatelocation, wherein the operating the wearable device in the private modeis further based on the location of the wearable device being a privatelocation.
 21. The wearable device of claim 17, wherein the one or moreprocessors are further configured to: determine that the electronicdevice is operating in a meeting mode, wherein the operating thewearable device in the public mode is further based on the electronicdevice operating in the meeting mode.
 22. The wearable device of claim17, wherein the user settings are received through the electronicdevice.